Scala DataStream&DataStreamUtils accessors fix #1574
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The PR contains two orthogonal approaches of fixing the access to
DataStreamUtils.collect
for a scala environment. One or both of the approaches can be merged.The first simply reexposes access to the underlying java
DataStream
, while the second effectively adds a scala API forDataStreamUtils
.I am in favor of adding both. Usage of the latter looks as follows:
At least the first commit should be merged asap as the fix was requested on the user mailing list. [1]
[1] https://mail-archives.apache.org/mod_mbox/flink-user/201602.mbox/%3CCAFqo6nQ24dtExjPOX%3DrSuWSww8skCH23Q8i7CJ3Ef5LYhDj2pA%40mail.gmail.com%3E